Non-disruptively merging coordinated timing networks

ABSTRACT

Coordinated timing networks are dynamically merged into a single coordinated timing network. This merge occurs without taking down any of the servers. Each server of the merged coordinated timing network has the same coordinated timing network identifier (CTN ID), and the merged coordinated timing network has one selected primary time server. Optionally, the merged coordinated timing network may include a backup time server and an arbiter.

This application is a continuation of co-pending U.S. patent application Ser. No. 14/920,940, filed Oct. 23, 2015, entitled “NON-DISRUPTIVELY MERGING COORDINATED TIMING NETWORKS,” which is hereby incorporated herein by reference in its entirety.

BACKGROUND

One or more aspects relate, in general, to coordinated timing networks, and in particular, to merging coordinated timing networks.

A Coordinated Timing Network (CTN) is a network in which multiple distinct computing systems maintain time synchronization to form the coordinated timing network. Systems in the coordinated timing network employ a message based protocol, referred to as a Server Time Protocol (STP), to pass timekeeping information between the systems over existing, high-speed data links. This enables the time of day (TOD) clocks at each system to be synchronized to the accuracy required in today's high-end computing systems. Since the protocol makes use of technology within a computing system, synchronization accuracy scales as technology improves. A computing system that provides time to other computing systems is referred to as a time server or server herein.

Within a coordinated timing network for STP, there is to be only one server acting as the source of time for the network (referred to as the primary time server). If there is more than one time source, the two sources could diverge leading to a data integrity exposure. Likewise, if there is no single server acting as the source of time for the network, the clocks on the multiple servers could drift apart, raising a data integrity exposure in that way.

Customers using the Server Time Protocol have encountered situations in which multiple coordinated timing networks are to be merged into a single coordinated timing network. However, to accomplish this, one or more of the servers needs to be brought down. This is very disruptive to the customers' business and usually means a loss of business and revenue.

SUMMARY

Shortcomings of the prior art are overcome and additional advantages are provided through the provision of a computer program product for managing coordinated timing networks. The computer program product includes a computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes determining that a plurality of coordinated timing networks are to be merged into a single coordinated timing network (CTN). The plurality of coordinated timing networks includes, at least, one coordinated timing network and another coordinated timing network, wherein the one coordinated timing network comprises one set of servers and the other coordinated timing network comprises another set of servers. A coordinated timing network is a network in which multiple distinct computing systems maintain time synchronization to form the coordinated timing network, and provides synchronization of time of day clocks of the multiple distinct computing systems. Based on determining that the plurality of coordinated timing networks are to be merged, the plurality of coordinated timing networks are merged into the single coordinated timing network. The merging is performed non-disruptively in that servers of the plurality of coordinated timing networks continue processing during the merging. The merging includes obtaining a new CTN identifier and a merge indicator by at least one other server of the other set of servers of the other coordinated timing network to be merged with the one set of servers of the one coordinated timing network. The merge indicator is set to indicate that the other set of servers is to be included in the single coordinated timing network. A new configuration is obtained by the at least one other server of the other coordinated timing network. The new configuration is employed to indicate that the other set of servers is to be a part of the single coordinated timing network.

Computer-implemented methods and systems relating to one or more aspects are also described and claimed herein. Further, services relating to one or more aspects are also described and may be claimed herein.

Additional features and advantages are realized through the techniques described herein. Other embodiments and aspects are described in detail herein and are considered a part of the claimed aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more aspects are particularly pointed out and distinctly claimed as examples in the claims at the conclusion of the specification. The foregoing and objects, features, and advantages of one or more aspects are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

FIG. 1 depicts one example of a coordinated timing network;

FIGS. 2A-2B depict servers of coordinated timing networks to be merged, in accordance with an aspect of the present invention;

FIG. 3 shows a result of merging coordinated timing networks, in accordance with an aspect of the present invention;

FIG. 4 depicts one embodiment of logic to merge coordinated timing networks into a single coordinated timing network, in accordance with an aspect of the present invention;

FIG. 5 depicts one example of a new stratum-1 configuration information block used in accordance with an aspect of the present invention;

FIG. 6 depicts one embodiment of a cloud computing node;

FIG. 7 depicts one embodiment of a cloud computing environment; and

FIG. 8 depicts one example of abstraction model layers.

DETAILED DESCRIPTION

In accordance with one or more aspects, multiple coordinated timing networks are merged into a single coordinated timing network (CTN). This may be driven by a number of situations, including, but not limited to, changes internal to a business, system consolidation efforts, business mergers and/or reversing a temporary splitting of a coordinating timing network. Previously, customers have merged coordinated timing networks by taking down the partitions (e.g., logical partitions of the server), changing the configuration, and then bringing the partitions back up again as members of a new CTN. This process of bringing down the partitions to merge the CTNs is costly and inefficient.

Thus, in accordance with an aspect of the present invention, a coordinated timing network merging capability is provided that enables a CTN merge to be carried out dynamically, without shutting down any of the partitions or the servers on which the partitions are running. That is, a merging capability is provided that enables customers to safely merge coordinated timing networks without enduring the expense of a system outage. When the merge is complete, the separate CTNs will be a part of a larger CTN sharing time and connectivity across the larger set of servers.

One embodiment of a coordinated timing network is described with reference to FIG. 1. In this example, a coordinated timing network 100 includes a plurality of servers 102 coupled to one another via one or more STP links 104. For example, the plurality of servers 102 includes Server A 102 a and Server B 102 b. Although in this example, two servers are depicted, coordinated timing network 100 may include additional servers. Each server is coupled to a support element 106, which is further coupled to a hardware management console 108. The hardware management console may be the same console or a different console for each support element.

As examples, each server is a central electronics complex based on the z/Architecture offered by International Business Machines Corporation (IBM); the hardware management console is, for instance, a personal computer, such as an Intel-based personal computer with a DVD-RAM (digital video disk-random access memory), as a particular example, or other type of computer or processing device that includes functionality to provide a standard interface for configuring and operating partitioned and SMP (Symmetric Multiprocessing) systems, such as System z offered by International Business Machines Corporation; and each support element is, for instance, a workstation coupled to the central electronics complex used for monitoring and operating a system. Example hardware management consoles and support elements are based on technology offered by International Business Machines Corporation. z/Architecture is a registered trademark of International Business Machines Corporation, Armonk, New York, USA. One embodiment of the z/Architecture is described in “z/Architecture Principles of Operation,” IBM Publication No. SA22-7832-10, March 2015, which is hereby incorporated herein by reference in its entirety.

Servers of multiple coordinated timing networks are depicted in FIGS. 2A-2B. Referring initially to FIG. 2A, a first coordinated timing network 100 a (referred to herein as CTN A) includes a plurality of servers 102 (e.g., servers 102 a-102 d), and each server 102 may include one or more partitions 200 (e.g., logical partitions). Each partition is part of a particular Sysplex (system complex of servers), and the sysplex of a particular partition is indicated by a letter (e.g., letter A, in this example). Thus, partitions 200 a are part of Sysplex A.

Further, in one example, one of the servers, e.g., server 102 a (also referred to herein as Server 1), is a primary time server (PTS) 210 a providing current time for coordinated timing network 100 a. Further, server 102 b is a backup time server (BTS) 212 a for coordinated timing network 100 a. Yet further, another server, e.g., server 102 c, is an arbiter (ARB) 214 a for coordinated timing network 100 a. The arbiter server facilitates determination of a failure of the primary time server. As shown in FIG. 2A, each server is part of one coordinated timing network as indicated by a CTN ID 250 a (e.g., CTN ID 1) in each server 102.

Although certain servers are indicated as providing the timing roles of primary time server, backup time server and arbiter, in one embodiment, these roles are provided by the servers in conjunction with their support elements.

Now, referring to FIG. 2B, a coordinated timing network 100 b (referred to herein as CTN B) includes, for instance, a plurality of servers, such as servers 102 e-102 g. Each server includes one or more partitions 200, and each partition is part of a sysplex, such as Sysplex B, as indicated by 200 b.

Further, in one example, one of the servers, server 102 e (also referred to herein as Server B), is a primary time server (PTS) 210 b providing current time for coordinated timing network 100 b. Further, server 102 f is a backup time server (BTS) 212 b for coordinated timing network 100 b. Yet further, another server, e.g., server 102 g, is an arbiter (ARB) 214 b for coordinated timing network 100 b. As shown in FIG. 2B, each server is part of one coordinated timing network as indicated by a CTN ID 250 b (e.g., CTN ID 2) in each server 102.

Again, although certain servers are indicated as providing the timing roles of primary time server, backup time server and arbiter, in one embodiment, these roles are provided by the servers in conjunction with their support elements.

Each CTN may have more or less servers than described herein. The number of servers depicted in each CTN is just an example.

Servers in a CTN that are in the synchronized state are assigned a value, referred to as a stratum level, that specifies the number of servers between it and a primary time server. A primary time server operates at a stratum level of 1; secondary time servers operate at a stratum level of 2 or above, which increases as the number of servers in the timing path to the stratum-1 increases. In general, the quality of timekeeping information decreases as the stratum level increases. A server that is unsynchronized is assigned a stratum level of 0.

In one example, a customer would like to merge the two coordinated timing networks of FIGS. 2A-2B into a single coordinated timing network, as depicted in FIG. 3. As shown in FIG. 3, a coordinated timing network 300 includes servers 102 a-102 d of coordinated timing network 100 a and servers 102 e-102 g of coordinated timing network 100 b. One of the servers (e.g., server 102 a) is selected as the primary time server 302 for coordinated timing network 300, another server (e.g., server 102 b) is selected as the backup time server 304, and yet a further server (e.g., server 102 c) is selected as an arbiter 306. Since the coordinated timing networks have been merged, server 102 e no longer has the role of primary time server, server 102 f no longer has the role of backup time server, and server 102 g no longer has the role of arbiter.

One embodiment of logic used to merge multiple coordinated timing networks into a single coordinated timing network is described with reference to FIG. 4. In one example, one or more processors of one or more support elements and/or one or more servers are used to perform aspects of the logic to merge the coordinated timing networks.

Referring to FIG. 4, initially the servers are connected via coupling links, STEP 400. For instance, a manual operation is performed to connect the cables, and an operator action is performed to configure these coupling links for use and to bring them online. With this set-up, server 102 e (i.e., Server B) registers itself, e.g., at its support element, as a probe into the PTS of server 102 a (i.e., Server 1), to enable server 102 e to read the time of the PTS, and to enable the PTS to recognize server 102 e in this regard. This establishes intent, and allows timing information to flow from server 102 a to server 102 e.

Additionally, server 102 e uses server 102 a as an external time source (ETS), STEP 402. Server 102 e steers toward the time presented by server 102 a, thus bringing it into synchronization with CTN 100 a time, STEP 404. For example, server 102 e steers its time of day clock (TOD) to the time provided by the time of day clock of server 102 a.

A determination is made as to whether the times are within a configured amount of one another, INQUIRY 408. If the times are not close enough, then processing continues at STEP 404. However, if the times are within the configured amount, then the clocks of CTN 100 a and CTN 100 b are considered synchronized, STEP 410.

Then, server 102 e requests server 102 a to generate and distribute a new configuration, STEP 412. In particular, server 102 e sends a message to server 102 a requesting server 102 a to generate and distribute a new stratum-1 configuration that includes configuration information for the merged CTN, STEP 412.

Based on the request, server 102 a creates a new stratum-1 configuration information block, and distributes this configuration information block, STEP 414.

As one example, with reference to FIG. 5, a new stratum-1 configuration information block 500 includes a plurality of fields that include configuration information, such as, for instance:

-   -   A primary stratum-1 node descriptor 502: This field is valid         when a single server, dual server or triad definition has been         specified in the configuration type field (discussed below) and         includes the node descriptor of the new primary stratum-1 node;     -   An alternate stratum-1 node descriptor 504: This field is valid         when a dual server or triad definition has been specified in the         configuration type field and includes the node descriptor of the         new alternate stratum-1 node (i.e., the backup time server);     -   An optional arbiter node descriptor 506: This field is valid         when a triad definition has been specified in the configuration         type field and includes the node descriptor of the new arbiter         node;     -   A stratum-1 configuration update time 508: This field includes a         timestamp that indicates when the values in this block are to         become current for the CTN;     -   A configuration type 510: This field specifies the type of         stratum-1 configuration, as defined below:         -   Null definition—None of the node descriptors are valid.         -   Single server definition—Only the primary stratum-1 node             descriptor is valid. In a single server configuration, if             the primary time server is lost, synchronized time for the             CTN is lost, since there is no backup.         -   Dual server definition—The primary stratum-1 and alternate             stratum-1 (backup time server) node descriptors are valid.             In a dual server configuration, a mechanism is provided for             an alternate server to be able to take over the role of an             active stratum-1 server for the CTN.         -   Triad definition—The primary stratum-1, alternate stratum-1             and arbiter node descriptors are valid. In a triad             configuration, a primary time server, a backup time server             and an arbiter are provided. The arbiter server may be used             to determine a failure of the primary time server.     -   A merge indicator 512: When the merge indicator (e.g., a bit) is         set to one, it indicates that this is a special configuration         that will be used to merge multiple coordinated timing networks         into one coordinated timing network. The systems that are         already a part of this CTN will simply activate this         configuration. However, the primary time source of the merging         CTN will add a CTN ID in this configuration block to match that         of the new CTN and send it out to all of the servers in its         configuration. At activation time, they will change their CTN ID         and merge into a single CTN.     -   A new CTN ID 514: This field specifies a new CTN identifier         identifying the new CTN.

Although various fields are described herein, more, less and/or different fields may be included in the new stratum-1 configuration information block without departing from a spirit of one or more aspects of the present invention.

Returning to FIG. 4, STEP 414, server 102 a populates the block with, for instance, the designated primary time server, the alternate time server, the arbiter, and/or an update time, as well as sets the merge indicator (e.g., to one). Then, server 102 a distributes the new stratum-1 configuration to the servers in CTN A and to the primary time server (e.g., server 102 e) in CTN B. For instance, server 102 a (e.g., optionally, using its support element) includes the configuration information block or at least an indication of the block in a request block of a command, such as an STP modify stratum-1 configuration command, and distributes that command to the servers in CTN A and to the primary time server in CTN B.

Server 102 e receives the command, reads the configuration, adds a modified CTN ID (i.e., the CTN ID of CTN 100 a) to the configuration block, and distributes it to the other servers in CTN 100 b, STEP 416. Thereafter, at the time indicated in the stratum-1 configuration, all of the servers of the two CTNs activate their configurations and become part of a single new coordinated timing network lead by server 102 a, STEP 418. This is accomplished without bringing down the servers and/or the partitions executing on the servers.

As a result of becoming a single CTN, each server has the same CTN ID as reflected in FIG. 3 at 310, and each server uses server 102 a as its time source.

Described in detail herein is a CTN merging capability that dynamically merges multiple coordinated timing networks into a single coordinated timing network without shutting down any of the partitions and/or servers. Although it is indicated herein that the servers perform or are involved in certain actions, these actions may be performed by the servers, by the support elements coupled to the servers and/or by a combination of the servers and the support elements. Thus, the term “component of a server” used herein may include the server, the support element, and/or the server with the support element.

One or more aspects may relate to cloud computing.

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for loadbalancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

Referring now to FIG. 6, a schematic of an example of a cloud computing node is shown. Cloud computing node 10 is only one example of a suitable cloud computing node and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless, cloud computing node 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 6, computer system/server 12 in cloud computing node 10 is shown in the form of a general-purpose computing device. The components of computer system/server 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including system memory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 7, illustrative cloud computing environment 50 is depicted. As shown, cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 7 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 8, a set of functional abstraction layers provided by cloud computing environment 50 (FIG. 7) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 8 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.

In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and merge processing 96.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

In addition to the above, one or more aspects may be provided, offered, deployed, managed, serviced, etc. by a service provider who offers management of customer environments. For instance, the service provider can create, maintain, support, etc. computer code and/or a computer infrastructure that performs one or more aspects for one or more customers. In return, the service provider may receive payment from the customer under a subscription and/or fee agreement, as examples. Additionally or alternatively, the service provider may receive payment from the sale of advertising content to one or more third parties.

In one aspect, an application may be deployed for performing one or more embodiments. As one example, the deploying of an application comprises providing computer infrastructure operable to perform one or more embodiments.

As a further aspect, a computing infrastructure may be deployed comprising integrating computer readable code into a computing system, in which the code in combination with the computing system is capable of performing one or more embodiments.

As yet a further aspect, a process for integrating computing infrastructure comprising integrating computer readable code into a computer system may be provided. The computer system comprises a computer readable medium, in which the computer medium comprises one or more embodiments. The code in combination with the computer system is capable of performing one or more embodiments.

Although various embodiments are described above, these are only examples. For example, computing environments of other architectures can be used to incorporate and use one or more embodiments. Further, different instructions, instruction formats, instruction fields and/or instruction values may be used. Many variations are possible.

Further, other types of computing environments can benefit and be used. As an example, a data processing system suitable for storing and/or executing program code is usable that includes at least two processors coupled directly or indirectly to memory elements through a system bus. The memory elements include, for instance, local memory employed during actual execution of the program code, bulk storage, and cache memory which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

Input/Output or I/O devices (including, but not limited to, keyboards, displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives and other memory media, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems, and Ethernet cards are just a few of the available types of network adapters.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising”, when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below, if any, are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of one or more embodiments has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain various aspects and the practical application, and to enable others of ordinary skill in the art to understand various embodiments with various modifications as are suited to the particular use contemplated. 

What is claimed is:
 1. A computer program product for managing coordinated timing networks, the computer program product comprising: a non-transitory computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising: determining that a plurality of coordinated timing networks are to be merged into a single coordinated timing network (CTN), the plurality of coordinated timing networks including, at least, one coordinated timing network and another coordinated timing network, wherein the one coordinated timing network comprises one set of servers including a first primary time server and the other coordinated timing network comprises another set of servers including a second primary time server, wherein each of the plurality of coordinated timing networks and the single coordinated timing network are networks in which multiple distinct computing systems maintain time synchronization of time of day clocks of the multiple distinct computing systems, wherein the first primary time server provides a time of day dock used to synchronize the one set of servers and the second primary time server provides a time of day dock used to synchronize the other set of servers; and based on determining that the plurality of coordinated timing networks are to be merged, merging the plurality of coordinated timing networks into the single coordinated timing network, wherein the merging is performed non-disruptively in that servers of the plurality of coordinated timing networks continue processing during the merging, and wherein the merging comprises: selecting the first primary time server to be a primary time server of the single coordinated timing network; registering the second primary time server with the first primary time server; based on the registering, the first primary time server providing a current time of day dock of the first primary time server to the second primary time server; the second primary time server steering the time of day dock of the second primary time server to the current time of the time of day dock of the first primary time server to synchronize the other coordinated timing network with the one coordinated timing network; determining that the time of day dock of the second primary time server is within a configured amount of time from the current time of the time of day dock of the first primary server; based on the determination that the time of day dock of the second primary time server is within the configured amount of time from the current time of the time of day dock of the first primary time server, requesting the first primary time server generate and distribute a new configuration for the single coordinated timing network; the first primary time server generating the new configuration including a new CTN identifier and a merge indicator, the merge indicator set to indicate that the new configuration will be used to merge the one coordinated timing network and the other coordinated timing network into the single coordinated timing network; distributing the new configuration to the one set of servers in the one coordinated timing network and to the other set of servers in the other coordinated timing network; and at an activation time indicated in the new configuration, each of the one set of servers and the other set of servers changing a CTN identifier to the new CTN identifier, and activating the new configuration to become pan of the single coordinated timing network.
 2. The computer program product of claim 1, wherein the new configuration comprises a new configuration block that includes the new configuration.
 3. The computer program product of claim 2, wherein the new configuration block comprises the merge indicator indicating the merging of the plurality of coordinated timing networks.
 4. The computer program product of claim 1, wherein the new configuration further includes another indication of which other server of the one set of servers or the other set of servers is to be a backup time server for the single coordinated timing network.
 5. A computer system for managing coordinated timing networks, the computer system comprising: a memory; and a processor in communication with the memory, wherein the computer system is configured to perform a method, said method comprising: determining that a plurality of coordinated timing networks are to be merged into a single coordinated timing network (CTN), the plurality of coordinated timing networks including, at least, one coordinated timing network and another coordinated timing network, wherein the one coordinated timing network comprises one set of servers including a first primary time server and the other coordinated timing network comprises another set of servers including a second primary time server, wherein each of the plurality of coordinated timing, networks and the single coordinated timing network are networks hi which multiple distinct computing systems maintain time synchronization of time of day clocks of the multiple distinct computing systems, wherein the first primary time server provides a time of day clock used to synchronize the one set of servers and the second primary time server provides a time of day clock used to synchronize the other set of servers; and based on determining that the plurality of coordinated timing networks are to be merged, merging the plurality of coordinated timing networks into the single coordinated timing network, wherein the merging is performed non-disruptively in that servers of the plurality of coordinated timing networks continue processing during the merging, and wherein the merging comprises: selecting the first primary time server to be a primary time server of the single coordinated timing network; registering the second primary time server with the first primary time server; based on the registering, the first primary time server providing a current time of day clock of the first primary time server to the second primary time server; the second primary time server steering the time of day clock of the second primary time server to the current time of the time of day clock of the first primary time server to synchronize the other coordinated timing network with the one coordinated timing network; determining that the time of day clock of the second primary time server is within a configured amount of time from the current time of the time of day clock of the first primary server; based on the determination that the time of day clock of the second primary time server is within the configured amount of time from the current time of the time of day clock of the first primary time server, requesting the first primary time server generate and distribute a new configuration for the single coordinated timing network; the first primary time server generating the new configuration including a new CTN identifier and a merge indicator, the merge indicator set to indicate that the new configuration will be used to merge the one coordinated timing network and the other coordinated timing network into the single coordinated timing network; distributing the new configuration to the one set of servers in the one coordinated timing network and to the other set of servers in the other coordinated timing network; and at an activation time indicated hi the new configuration, each of the one set of servers and the other set of servers changing a CTN identifier to the new CTN identifier, and activating the new configuration to become part of the single coordinated timing network.
 6. A computer-implemented method of managing coordinated timing networks, the computer-implemented method comprising: determining that a plurality of coordinated timing networks are to be merged into a single coordinated timing network (CTV), the plurality of coordinated timing networks including, at least, one coordinated timing network and another coordinated timing network, wherein the one coordinated timing network comprises one set of servers including a first primary time server and the other coordinated timing network comprises another set of servers including a second primary time server, wherein each of the plurality of coordinated timing networks and the single coordinated timing network are networks in which multiple distinct computing systems maintain time synchronization of time of day clocks of the multiple distinct computing systems, wherein the first primary time server provides a time of day clock used to synchronize the one set of servers and the second primary time server provides a time of day clock used to synchronize the other set of servers; and based on determining that the plurality of coordinated timing networks are to be merged, merging the plurality of coordinated timing networks into the single coordinated timing network, wherein the merging is performed non-disruptively in that servers of the plurality of coordinated timing networks continue processing during the merging, and wherein the merging comprises: selecting the first primary time server to be a primary time server of the single coordinated timing network; registering the second primary time server with the first primary time server; based on the registering, the first primary time server providing a current time of day dock of the first primary time server to the second primary time server; the second primary time server steering the time of day dock of the second primary time server to the current time of the time of day dock of the first primary time server to synchronize the other coordinated timing network with the one coordinated timing network; determining that the time of day dock of the second primary time server is within a configured amount of time from the current time of the time of day dock of the first primary server; based on the determination that the time of day dock of the second primary time server is within the configured amount of time from the current time of the time of day dock of the first primary time server, requesting the first primary time server generate and distribute a new configuration for the single coordinated timing network; the first primary time server generating the new configuration including a new CTN identifier and a merge indicator, the merge indicator set to indicate that the new configuration will be used to merge the one coordinated timing network and the other coordinated timing network into the single coordinated timing network; distributing the new configuration to the one set of servers in the one coordinated timing network and to the other set of servers in the other coordinated timing network; and at an activation time indicated in the new configuration, each of the one set of servers and the other set of servers changing a CT N identifier to the new CTN identifier, and activating the new configuration to become part of the single coordinated timing network.
 7. The computer-implemented method of claim 6, wherein the new configuration comprises a new configuration block that includes the new configuration, the new configuration block comprising the merge indicator indicating the merging of the plurality of coordinated timing networks. 